IDM 3.0 User Guide

This page explains how end users work with IDM 3.0, starting with login and the Admin Console features used to manage applications, catalogues, action types, and rule structures.

Contents

• Admin Console
• Application
• Global Field Catalogue
• Application Field Catalogue
• Action Type
• Rule Maintenance Set
• Rule Set
• Modelling
• Manage Decision
• Rule Simulation

Requirement and scope

Intelligent Decision Management (IDM) is one of the key solutions in Incture's application suite. IDM helps organizations digitize and automate business scenarios in a user-friendly way by separating decision logic from application logic. It provides a web-based application to define metadata, model decision blocks, author decision rules, and govern those rules for use in business applications.

IDM is an enterprise business rules management product designed to streamline the full lifecycle management of business rules across the enterprise landscape.

Application overview

Application login

IDM uses a secure authentication page as the entry point to the application. Users must provide valid credentials, such as username or email and password, to access the system.

If a user does not have the required IDM role access, the user will see a not-authenticated screen.

After a successful login, the user is taken to the IDM home page.

Admin Console

The Admin Console is used to create and manage core IDM configuration objects. It contains the following submodules:

• Application
• Global Field Catalogue
• Application Field Catalogue
• Action Type
• Rule Set
• Rule Maintenance Set
• Event Logs

By default, when the user opens the Admin Console, the system lands on the Application module.

Application

The Application module is used to create and manage applications within IDM.

When the user opens the module, the Application summary screen displays:

• A list of existing applications
• An option to create a new application

Create a new application

To create an application:

1. Click Create New on the Application summary screen.
2. Enter the following fields in the popup:

• Name (mandatory)
• Label (mandatory)
• Description (optional)

The Continue button remains disabled until Name and Label are entered.

After entering the required details:

1. Click Continue.
2. The system navigates to the Application Field Catalogue screen.

Application Field Catalogue during application creation

To add field catalogues to the application:

1. Click Add.
2. A popup displays all existing Application Field Catalogues (AFCs).
3. The popup also provides an Add New option.

Add an existing AFC

1. Select the required AFC from the list.
2. Click Add.
3. The selected AFC is added to the application.

Cancel in the add popup

If the user clicks Cancel in the popup:

• The popup closes
• Any current selections are discarded
• No changes are saved

Create a new AFC from application creation

If a new Application Field Catalogue is needed:

1. Click Add New.
2. Enter:

• Name
• Label
• Description

The screen also displays the list of existing Global Field Catalogues (GFCs).

3. Select the required GFCs.
4. Click Save.

A confirmation popup is displayed.

5. Click Confirm.

After confirmation:

• The new AFC is created successfully
• A success message is shown
• The newly created AFC is automatically added to the application

Action Type during application creation

After saving the required Application Field Catalogues:

1. Click Next.
2. The system navigates to the Action Type screen.

Add an existing Action Type

1. Click Add.
2. A popup displays all existing Action Types.
3. Select the required Action Type.
4. Click Add.

The selected Action Type is added to the application successfully.

Create a new Action Type

1. Click Add New in the popup.
2. Enter:

• Name
• Label
• Description

3. Click Save.
4. A confirmation popup is displayed.
5. Click Ok.

The new Action Type is created and added to the application.

Rule Maintenance Set during application creation

After completing the Action Type configuration:

1. Click Next.
2. The system navigates to the Rule Maintenance Set screen.
3. Click Add.
4. Enter:

• Name
• Label
• Description

5. Click Save.

A confirmation popup is displayed.

6. Click OK.

The Rule Maintenance Set is created successfully and a success message is displayed.

Cancel functionality

If the user clicks Cancel, the confirmation popup closes.

Rule Set during application creation

After completing the Rule Maintenance Set configuration:

1. Click Next.
2. The system navigates to the Rule Set screen.

Add an existing Rule Set

1. Click Add.
2. A popup displays all existing Rule Sets.
3. Select the required Rule Set.
4. Click Add.

The selected Rule Set is added to the application successfully.

Create a new Rule Set

1. Click Add New.
2. Enter:

• Rule Maintenance Set from the dropdown
• Name
• Label
• Description

The previously created Rule Maintenance Set is available for selection.

3. In the Action Types section, select the required action types already configured for the application.
4. Click Save.

After saving, a confirmation message indicates that the Rule Set has been created successfully.

Save the application as draft

After filling the required details:

1. Click Save as Draft.
2. A confirmation message is displayed.
3. Click OK.

The system returns to the Application summary screen and the application status is displayed as Draft.

Edit and publish a draft application

1. On the Application summary screen, click the Edit icon.
2. The application opens in edit mode.
3. Click Publish.
4. A confirmation message is displayed.

After publishing:

• The application is published successfully
• The application status changes to Active

Global Field Catalogue

The Global Field Catalogue module is used to create and manage reusable field definitions.

Scenario 1: Create a GFC without value help

1. Navigate to Admin Console.
2. Select Global Field Catalogue.
3. Click Create New.
4. Enter:

• Name
• Label
• Description

5. In the Data Element field, click the lookup icon.
6. Select the required Data Element from the list.
7. Click Publish.

A confirmation message is displayed. After confirmation, the GFC is created successfully.

Scenario 2: Create a GFC with static value help

1. Navigate to Admin Console.
2. Select Global Field Catalogue.
3. Click Create New.
4. Enter:

• Name
• Label
• Description

5. Select the required Data Element using lookup.
6. Enable the Value Help toggle.

The following options are displayed:

• Static Value Help (default)
• API Based
• DB Based

7. Keep Static Value Help selected.
8. Enter:

• Key
• Value
• Additional Text if required

9. Click Add to create additional entries.

If required, use Delete next to an entry to remove it.

The system does not allow publishing unless every added entry has both Key and Value.

10. Click Publish.

After confirmation, a success message is displayed and the GFC is created successfully.

Scenario 3: Create an API-based GFC

1. Navigate to Admin Console.
2. Select Global Field Catalogue.
3. Click Create New.
4. Enter:

• Name
• Label
• Description

5. Select the required Data Element using the lookup.
6. Enable the Value Help toggle.
7. Select API Based.

In the Define URL section, enter:

• Destination URL using the value help icon
• Value Help URL
• API Type as REST or OData
• Method Type as GET or POST
• Response Path for the JSON or XML path

In the Fields section:

1. Click Add.
2. For the first row, the default GFC name is shown in the Field column and cannot be edited.
3. Enter the Display Name and Mapped Name.
4. Click Preview to preview the added fields.
5. Click Publish.

After confirmation, a success message is displayed.

Scenario 4: Create a DB-based GFC

1. Navigate to Admin Console.
2. Select Global Field Catalogue.
3. Click Create New.
4. Enter:

• Name
• Label
• Description

5. Select the required Data Element using lookup.
6. Enable the Value Help toggle.
7. Select DB Based.

Then configure:

• Host using value help
• Data Table using value help

In the Fields section:

1. Click Add.
2. The first field shows the default GFC name and cannot be edited.
3. Enter Display Name.
4. Select Mapped Name using value help.

To add more fields:

1. Click Add again.
2. Enter Display Name and Mapped Name for each row.
3. Click Preview.
4. Click Publish.

After confirmation, the DB-based GFC is created successfully.

Search for a GFC

Users can search existing GFCs from the GFC Summary screen:

1. Enter the GFC name or part of it in the search field.
2. The system displays matching results.
3. Select the required GFC to view or edit.

Notes for GFC

• Duplicate GFC names are not allowed
• Users can edit an existing GFC from the summary screen using Edit
• Users cannot publish a GFC unless all mandatory fields are completed correctly

Application Field Catalogue

The Application Field Catalogue module is used to create application-specific catalogue groupings using one or more GFCs.

Create a new AFC

1. Navigate to Admin Console.
2. Select Application Field Catalogue.
3. On the AFC Summary screen, click Create New.
4. Enter:

• Application Field by selecting the application from the dropdown
• Name
• Label
• Description
• GFC Selection by choosing one or more Global Field Catalogues

To save in draft status, click Save as Draft.

To make the AFC active, click Publish.

Delete an AFC

1. On the AFC Summary screen, locate the required AFC.
2. Click Delete.
3. Confirm the deletion.

Behavior:

• If the AFC has no mapped GFCs, it is deleted successfully
• If the AFC has mapped GFCs, deletion is blocked and an error message is shown

Edit an AFC

1. On the AFC Summary screen, locate the AFC.
2. Click Edit.
3. Update the required fields.

Users can edit all details except the AFC Name.

4. Click Publish.
5. Confirm the message.

The AFC is updated successfully.

Notes for AFC

• Duplicate AFC names are not allowed
• Users cannot publish an AFC without completing all mandatory fields

Action Type

The Action Type module is used to manage available action definitions used in rule configuration.

Create a new Action Type

1. Navigate to Admin Console.
2. Select Action Type.
3. The Action Type Summary screen is displayed.
4. Click Create New.

The Create Action Type screen opens.

Fill in:

• Name
• Label
• Description
• GFC Selection by choosing one or more Global Field Catalogues to map

To save in draft status, click Save as Draft.

To make the Action Type active, click Publish.

Edit an Action Type

1. On the Action Type Summary screen, locate the required Action Type.
2. Click Edit.
3. Update the required fields.

Users can edit all details except the Action Type Name.

4. Click Publish.
5. Confirm the message.

The Action Type is updated successfully.

Delete an Action Type

1. On the Action Type Summary screen, locate the required Action Type.
2. Click Delete.
3. Confirm the deletion.

Behavior:

• If the Action Type has no mapped GFCs, it is deleted successfully
• If the Action Type has mapped GFCs, deletion is blocked and an error message is shown

Search for an Action Type

1. Use the search field on the Action Type Summary screen.
2. Enter the Action Type name or part of it.
3. Matching results are displayed below the search bar.
4. Select an Action Type from the results to view, edit, or delete it.

Notes for Action Type

• Duplicate Action Type names are not allowed
• Users cannot publish an Action Type without completing all mandatory fields

Rule Maintenance Set

The Rule Maintenance Set module is used to group and manage related rule sets for an application.

Create a new Rule Maintenance Set

1. Navigate to Admin Console.
2. Select Rule Maintenance Set.
3. The RMS Summary screen is displayed.
4. Click Create New.

The Create Rule Maintenance Set screen opens.

Fill in:

• Application by selecting the application from the dropdown
• Name
• Label
• Description
• Mapped Rule Sets optionally by selecting one or more existing rule sets

5. Click Publish.

A confirmation message is displayed indicating the Rule Maintenance Set was created successfully.

Edit a Rule Maintenance Set

1. On the RMS Summary screen, locate the required RMS.
2. Click Edit.
3. Update the required fields.

Users can edit all details except the RMS Name.

4. Click Publish.

A confirmation message indicates that the RMS has been updated successfully.

Delete a Rule Maintenance Set

1. On the RMS Summary screen, locate the required RMS.
2. Click Delete.
3. Confirm the deletion.

Behavior:

• If the RMS has no mapped rule sets, it is deleted successfully
• If the RMS has mapped rule sets, deletion is blocked and an error message is shown

Search for a Rule Maintenance Set

1. Use the search field on the RMS Summary screen.
2. Enter the RMS name or part of it.
3. Matching results are displayed below the search bar.
4. Select an RMS from the results to view, edit, or delete it.

Notes for Rule Maintenance Set

• Duplicate RMS names are not allowed
• Users cannot publish an RMS without completing all mandatory fields

Rule Set

The Rule Set module is used to define the field and action structure used by modelled rules.

Create a new Rule Set

1. Navigate to Admin Console.
2. Select Rule Set.
3. The Rule Set Summary screen is displayed.
4. Click Create New.

The Create Rule Set screen opens.

Configure:

• Rule Maintenance Set
• Name
• Label
• Description
• Required fields in the Fields section
• The appropriate Action Type to map to the Rule Set

To save in draft status, click Save as Draft.

A confirmation message indicates the Rule Set was saved as draft.

To make the Rule Set active, click Publish.

A confirmation message indicates the Rule Set was created successfully and is now active.

Edit a Rule Set

1. On the Rule Set Summary screen, locate the required Rule Set.
2. Click Edit.
3. Update the required fields.

Users cannot edit:

• Rule Maintenance Set
• Name

4. Click Publish.
5. Confirm the message.

The Rule Set is updated successfully.

Delete a Rule Set

1. On the Rule Set Summary screen, locate the required Rule Set.
2. Click Delete.
3. Confirm the deletion.

The Rule Set can be deleted only when there are no mapped fields. If mapped fields exist, deletion is blocked and an error message is shown.

Notes for Rule Set

• Duplicate Rule Set names are not allowed
• Users cannot publish a Rule Set without completing all mandatory fields
• Rule Maintenance Set and Name cannot be edited after creation

Modelling

The Modelling module is used to create and configure Decision Tables, Text Rules, and Rule Chains.

Navigate to Modelling

1. Log in to IDM.
2. Click Modelling.
3. The Modelling screen is displayed.

On the left panel, users can view all existing applications.

After selecting an application:

• The top section displays linked Rule Maintenance Sets and their Rule Sets
• The breadcrumb shows the current path as Application Name > RMS Name > RS Name

Create a Decision Table

1. Navigate to Modelling.
2. Select an application.
3. The following tabs are displayed:

• All Rules
• Decision Tables
• TextRules
• Rule Chain

The count of rules is displayed in each tab.

4. Click Create New.
5. In the Create Rule popup, enter:

• Name
• Label
• Effective Date
• Description

6. Select the required Rule Type as Decision Table.
7. Click Continue.

Decision Table configuration

After clicking Continue, the system navigates to the Configuration section.

Rule Execution Sequence

By default, the Rule Execution Sequence is Exclusive.

Available options:

• Exclusive: displays only the first or best matching result
• Inclusive: displays all matching results
• Unique: displays exactly one unique matching record
• Collect: aggregates results for action fields

Only one option can be selected at a time.

Restrict Duplicates

This field appears when Inclusive is selected.

Available options:

• None
• Conditions Only
• Conditions and Actions

Validity Period

Users must choose one option:

• Date
• Timestamp
• N/A

Behavior:

• Date: users select a valid date
• Timestamp: users select both date and time
• N/A: no validity value is required

Only one radio button can be selected at a time.

Additional configuration options

• Expression Language: enables expression entry when selected
• Valuehelp Dependent: enforces field dependencies in Manage Decision
• Orchestration: enables input and output field selection and rule chaining
• Tree Hierarchy Representation: creates the Decision Table in tree view instead of standard tabular format
• Value Help Representation: controls how value help is shown, defaulting to key-value format
• Titles Required on Export: includes titles in exported Excel files
• Autosequence: enables auto-sequence support for integer and decimal fields
• Excel Import Options: allows either Validate and Display on UI or Validate and Save to DB

Decision Table field selection flow

1. After completing Configuration, click Next.
2. In Conditions, select one or more conditions.

You cannot proceed to Actions without selecting at least one condition.

3. Click Next.
4. In Actions, select the required actions.
5. Click Next to open Map Functionalities.

Map Functionalities for Decision Table

Users can configure field-level settings such as:

• Default Value
• Editable
• Mandatory
• Visible
• Multiselect
• Editable on Update
• Editable on Export
• Autosequence

Behavior:

• If Editable is deselected, the field cannot be edited in Manage Decision
• If Editable is deselected, Default Value becomes mandatory
• If Mandatory is selected, the field must be filled
• If Visible is deselected, the field is hidden in Manage Decision
• If Multiselect is enabled, multiple values can be selected
• If Editable on Update is disabled, the field cannot be changed after creation
• If Editable on Export is disabled, the field is not editable in exported Excel

Preview, save draft, and publish a Decision Table

After configuration:

1. Click Preview to see the configured Decision Table.
2. Click Save as Draft to store the Decision Table in draft status.
3. From the summary screen, click Edit on the draft Decision Table.
4. Click Publish.

After confirmation, the Decision Table status changes to Active.

Create a Text Rule

1. Navigate to Modelling.
2. Select an application.
3. Open Text Rules.
4. Click Create New.
5. Enter:

• Name
• Label
• Effective Date
• Description

6. Select the Rule Type as Simple or Advanced.
7. Click Continue.

Configuration flow:

1. Select the Rule Execution Sequence.
2. Optionally enable Titles Required on Export.
3. Click Next to move to Conditions.
4. Select one or more conditions.
5. Click Next to move to Actions.
6. Select the required actions.
7. Click Next to move to Map Functionalities.
8. Enter default values if needed.
9. Click Preview.
10. Click Save as Draft.

To publish:

1. Return to the summary screen.
2. Click Edit.
3. Open the Text Rule.
4. Click Publish.

Manage blocks in a Text Rule

Users can:

• Add a new block using Add
• Edit a block name using the edit icon
• Delete a block using Delete
• View block expressions using the expression icon
• Copy and paste blocks using the three-dot menu
• View audit history using Audit Log
• Export blocks using the export icon
• Import blocks through the three-dot menu
• View Activity Log
• Set or remove a default block
• Save blocks as draft
• Publish draft blocks

Text Rule notes:

• In Simple Text Rule, condition value types such as Value, Variable, Expression, and Null are not available
• Simple Text Rule has limited advanced condition handling
• Simple Text Rule supports an ELSE option in the Actions section
• Advanced Text Rule supports richer condition and action configuration

Create a Rule Chain

1. Navigate to Modelling.
2. Select an application.
3. Click Create New.
4. Enter:

• Name
• Label
• Description
• Effective Date

5. Select Rule Type as RuleChain.
6. Click Continue.

The Rule Chain workspace opens and allows drag-and-drop configuration.

Users can create Rule Chains using:

• Decision Tables
• Simple or Advanced Text Rules
• A combination of Decision Tables and Text Rules

When configured nodes share a common node, the system connects them automatically. If not, the system displays No Common Node.

To save:

1. Click Save as Draft.
2. Confirm the message.

The Rule Chain status is set to Draft.

To publish:

1. Open the Rule Chain from the summary screen using Edit.
2. Click Publish.
3. Confirm the message.

The Rule Chain status changes to Active.

Manage Decision

The Manage Decision module is used to maintain active Decision Tables and Text Rules after they are published from Modelling.

Navigate to Manage Decision

1. Open IDM.
2. Click Manage Decision.
3. The Manage Decision screen is displayed.

Only active Decision Tables are displayed in this module.

View applications, RMS, and Rule Sets

On the left panel:

• Applications are displayed
• Selecting an application shows Rule Sets under the selected RMS

Displayed columns include:

• Name
• Description
• Rule Type
• Version
• Rule / Block
• Modified By
• Modified On

Tabs and search

Available tabs:

• All Rules
• Decision Table
• Text Rule

Search behavior:

• Exact matches are shown for full rule names
• Partial matches are supported
• If nothing matches, No record found is displayed

View rule details

1. Locate the required rule.
2. Open the three-dot menu.
3. Select Details.

A side panel opens and displays complete rule details.

Manage records in a Decision Table

To edit a Decision Table:

1. Locate the required Decision Table.
2. Open the three-dot menu.
3. Select Edit.

Users can then manage records as defined by the Decision Table configuration.

Add a record

1. Click Quick Add.
2. A new row is added.
3. Enter the required field values.
4. Click Validate.
5. If validation succeeds, click Done.
6. Click Save.

Status behavior:

• After adding a record, status is Created
• After validation and save, status becomes Draft Created

Field behavior:

• Lookup-enabled fields use value help
• Non-lookup fields require manual entry
• Autosequence auto-populates sequence values
• Default Value is auto-filled when configured
• Multiselect allows multiple selections
• Mandatory fields must be filled before validation

Edit a record

1. Open the Decision Table in edit mode.
2. Update the required values.
3. Click Validate.
4. Click Save.

If a field is not editable or not editable on update, it cannot be changed.

After saving, the status changes to Draft - Modified.

Delete a record

1. Select the required record.
2. Click Delete.
3. Confirm the deletion.

The record is removed successfully.

Duplicate record handling

If a newly entered record matches an existing active record:

• The system does not allow two active duplicate records
• The existing active record is deactivated
• The new record is added with the latest details

Copy and paste records

1. Open the Decision Table in edit mode.
2. Use the three-dot menu on a row.
3. Select Copy.
4. Choose Paste Before or Paste After.
5. Click Validate.
6. Click Save.

View Change Log

1. Open the row-level three-dot menu.
2. Select Change Log.

The log shows:

• Updated field values
• User who made the change
• Date and time of the change

View Activity Log

1. Open the required Decision Table.
2. Click Activity Log.

Tracked activities include:

• Record Added
• Record Validated
• Record Saved
• Record Deleted

Table customization and variants

The Table Customization popup supports:

• Columns
• Filter
• Grouping
• Sort

Users can:

• Pin columns
• Filter records
• Sort records
• Save these configurations as variants
• Set variants as default or global

Export and import Decision Tables

Users can export:

• Decision Table template
• Decision Table data

Users can also import Decision Tables by selecting the Excel file through the three-dot menu and uploading a valid sheet with all mandatory fields completed.

Static view

Users can open the static view of a Decision Table from Manage Decision.

Manage Text Rules

For Text Rules in Manage Decision, users can:

• Edit conditions and actions
• Choose value types such as Value, Variable, Expression, Null, Object, or Key-Value where supported
• Add multiple conditions and actions
• Use AND and OR logic between conditions
• Add, edit, copy, paste, export, import, and delete blocks
• View block audit and activity logs
• Set a block as default or remove default
• Save blocks as draft
• Publish draft blocks

Rule Simulation

The Rule Simulation module is used to test active Decision Tables, Text Rules, and Rule Chains before productive use.

Open Rule Simulation

1. Click Rule Simulation.
2. The Rule Simulation Summary screen is displayed.

Create a new Rule Simulation for a Decision Table

1. On the Rule Simulation Summary screen, click Create New.
2. The Create Rule Simulation screen is displayed.
3. Enter the simulation name in the Name field.
4. In the Rule Name field, click value help.
5. A lookup window displays all active rules.
6. Select the required Decision Table.

After the rule is selected:

• The latest version is shown by default in the Version field
• If a different version is needed, use value help in Version and select the required version

7. Click Add.

The available Decision Table conditions are displayed.

8. Enter or select valid values in the condition fields.
9. If a condition is not needed, click Remove (-) to remove it.
10. Click Simulate.

Behavior:

• If the entered values are valid, the system simulates the rule and displays the corresponding actions
• If no rule condition matches, the system displays No actions displayed

11. Click Preview to view the Decision Table preview.
12. Click Save.
13. Confirm the message.

The simulation is saved successfully.

Simulate a Simple Text Rule or Advanced Text Rule

1. Open Rule Simulation.
2. Click Create New.
3. Enter the simulation name in the Name field.
4. In Rule Name, click value help.
5. Select the required Simple Text Rule or Advanced Text Rule from the list of active rules.

After selection:

• The latest version is shown by default
• If a different version is needed, use value help in the Version field

6. Click Add.
7. The available conditions are displayed.
8. Enter valid values in the condition fields.
9. Remove unnecessary conditions using Remove (-) if required.
10. Click Simulate.

Behavior:

• If the entered values are valid, the system displays the corresponding actions
• If the values do not match the rule logic, the system displays No actions displayed

11. Click Preview to view the rule preview.
12. Click Save.
13. Confirm the message.

The rule simulation is saved successfully.

Simulate a Rule Chain

1. Open Rule Simulation.
2. Click Create New.
3. Enter the simulation name in the Name field.
4. In Rule Name, click value help.
5. Select the required Rule Chain from the list of active rules.
6. Click Add.

The available conditions for the Rule Chain are displayed.

7. Enter or select values for the required conditions.
8. Click Simulate.

The available actions are displayed.

9. Click Preview to view the selected rule.
10. Click Save.
11. Confirm the message.

The Rule Simulation is created successfully.

Rule Content Packaging

Rule Content Packaging is available from Admin Console > System Settings and is used to export or import application configuration and rule content as JSON.

Open Rule Content Packaging

1. Click Admin Console.
2. Select System Settings.
3. The system navigates to the Rule Content Packaging screen.

Export an application with rule data

1. In Rule Content Packaging, keep Export selected.
2. In Selected Application, choose the application to export.
3. In Export Application, select Full Application with Rule Data.

The system displays the full application content, including:

• Rule Maintenance Sets
• Rule Sets
• Decision Tables
• Text Rules
• Rule Chains

The displayed rule data is read-only.

Users can:

• Click the eye icon beside a Decision Table to view its records
• Click the eye icon beside a Text Rule to view its blocks

4. Click Export as JSON.
5. Confirm the export.

The system exports the full application along with rule data as a JSON file.

Export an application without rule data

1. Open Admin Console > System Settings.
2. Keep Export selected.
3. Choose the required application in Selected Application.
4. In Export Application, select Full Application without Rule Data.

The system displays the application structure in read-only mode, including:

• Rule Maintenance Sets
• Rule Sets
• Decision Tables
• Text Rules
• Rule Chains

Users can still preview Decision Table records and Text Rule blocks using the eye icon.

5. Click Export as JSON.
6. Confirm the export.

The system exports the full application without rule data as a JSON file.

Export partial or delta content

1. Open Admin Console > System Settings.
2. Keep Export selected.
3. Choose the application in Selected Application.
4. In Export Application, select Partial/Delta.

The system displays the full application structure.

Users can select specific components to export, such as:

• Selected Rule Maintenance Sets
• Selected Rule Sets
• Selected Decision Tables
• Selected Text Rules

Users can preview Decision Table records and Text Rule blocks using the eye icon.

5. Click Export as JSON.
6. Confirm the export.

The system exports the selected components as a JSON file.

Import an application

1. Open Admin Console > System Settings.
2. Select Import.
3. Click Choose File.
4. Select the JSON file from your system.
5. Click Validate Document.

After successful validation, a confirmation message is displayed.

6. Click Import.

Import behavior:

• If the JSON contains partial data, only the partial data is imported
• If the JSON contains complete rule data, all rules are imported
• If the JSON contains no rule data, only the non-rule application structure is imported